Course Name | Design Patterns and Code Refactoring |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
CE 611 | Fall/Spring | 3 | 0 | 3 | 7.5 |
Prerequisites | None | |||||
Course Language | English | |||||
Course Type | Elective | |||||
Course Level | Third Cycle | |||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | ||||||
Course Coordinator | - | |||||
Course Lecturer(s) | ||||||
Assistant(s) | - |
Course Objectives | The goal of this course is an in depth study of design patterns and code refactoring. Design Patterns enable software professionals to avoid designing solutions from scratch which have been worked before, while refactoring studies techniques to root out bugs and identify and correct poorly structured code without changing the external behavior of the system. Design patterns improve the design “before code is written”, refactoring improves the design “after code is written”. Both design patterns and refactoring techniques allow the development of complex maintainable and extensible software systems. The pros and cons of each technique will be discussed and the students shall get an opportunity to apply these techniques through hands-on assignments |
Learning Outcomes | The students who succeeded in this course;
|
Course Description | This course is an in depth study of design patterns and code refactoring techniques which is used to develop complex, maintainable and extendible sofware systems. |
Related Sustainable Development Goals | |
| Core Courses | |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction to design patterns and the catalog of design patterns. Strategy | Chapter 1 Design Patterns. Gamma, Helm, Johnson and Vlissides (GHJV). |
2 | Creational Patterns: Abstract Factory, Builder, Prototype | Chapter 3 Design Patterns. Gamma, Helm, Johnson and Vlissides (GHJV). |
3 | Structural patterns-Part 1: Adapter,Composite, Facade | Chapter 4 Design Patterns. Gamma, Helm, Johnson and Vlissides (GHJV). |
4 | Structural patterns-Part 2: Bridge, Decorator | Chapter 4 Design Patterns. Gamma, Helm, Johnson and Vlissides (GHJV). |
5 | Behavorial patterns-Part 1: Observer, Mediator, Template Method | Chapter 5 Design Patterns. Gamma, Helm, Johnson and Vlissides (GHJV). |
6 | Behavorial patterns-Part 2: Memento, State | Chapter 5 Design Patterns. Gamma, Helm, Johnson and Vlissides (GHJV). |
7 | Midterm | |
8 | Introduction to Refactoring. Bad Code Smells | Chapters 1-3 Refactoring. Fowler et.al. pp. 1-87. |
9 | Managing Data | Chapter 8 Refactoring. Fowler et.al. pp 169-232. |
10 | Removing Conditional Logic | Chapter 9 Refactoring. Fowler et.al. pp. 237-267. |
11 | Refactoring Towards Simplicity | Chapter 10 Refactoring. Fowler et.al. pp. 271-315. |
12 | Generalization Refactorings | Chapter 11 Refactoring. Fowler et.al. pp. 319-355. |
13 | Student Presentations | |
14 | Student Presentations | |
15 | Review | |
16 | Final |
Course Notes/Textbooks | “Design patterns: Elements of Reusable Object-Oriented Software” by E. Gamma, R. Helm, R. Johnson and J. Vlissides.Addison-Wesley. 1995. ISBN-13: 978-0-201-63361, ISBN-10: 0-201-63361-2 “Refactoring, Improving the design of existing code” by Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts. 1999 ISBN-13: 978-0-201-48567-7, ISBN-10: 0-201-48567-2 |
Suggested Readings/Materials | Instructor slides. |
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | 1 | 20 |
Project | 1 | 20 |
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 30 |
Final Exam | 1 | 30 |
Total |
Weighting of Semester Activities on the Final Grade | 3 | 70 |
Weighting of End-of-Semester Activities on the Final Grade | 1 | 30 |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | 15 | 4 | 60 |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | |||
Presentation / Jury | 1 | 30 | |
Project | 1 | 30 | |
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 20 | |
Final Exams | 1 | 37 | |
Total | 225 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Accesses information in breadth and depth by conducting scientific research in Computer Engineering, evaluates, interprets and applies information. | |||||
2 | Is well-informed about contemporary techniques and methods used in Computer Engineering and their limitations. | |||||
3 | Uses scientific methods to complete and apply information from uncertain, limited or incomplete data, can combine and use information from different disciplines. | |||||
4 | Is informed about new and upcoming applications in the field and learns them whenever necessary. | |||||
5 | Defines and formulates problems related to Computer Engineering, develops methods to solve them and uses progressive methods in solutions. | |||||
6 | Develops novel and/or original methods, designs complex systems or processes and develops progressive/alternative solutions in designs. | |||||
7 | Designs and implements studies based on theory, experiments and modelling, analyses and resolves the complex problems that arise in this process. | |||||
8 | Can work effectively in interdisciplinary teams as well as teams of the same discipline, can lead such teams and can develop approaches for resolving complex situations, can work independently and takes responsibility. | |||||
9 | Engages in written and oral communication at least in Level B2 of the European Language Portfolio Global Scale. | |||||
10 | Communicates the process and the results of his/her studies in national and international venues systematically, clearly and in written or oral form. | |||||
11 | Is knowledgeable about the social, environmental, health, security and law implications of Computer Engineering applications, knows their project management and business applications, and is aware of their limitations in Computer Engineering applications. | |||||
12 | Highly regards scientific and ethical values in data collection, interpretation, communication and in every professional activity. |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest